Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 70a843856a4501efde2eab8deab3e48ca7edead133f2c9b6ae4f90ee75dc50b2

Tx prefix hash: 863c081a9c21d702a3e207ee727641e638f55ce5654854f1056696f713e6226a
Tx public key: 4466ac044a755f27b61966d8beb1b0f94af10e810c3a0d5266049aa39f8a29d0
Timestamp: 1727554458 Timestamp [UCT]: 2024-09-28 20:14:18 Age [y:d:h:m:s]: 00:188:09:55:39
Block: 1120188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134459 RingCT/type: yes/0
Extra: 014466ac044a755f27b61966d8beb1b0f94af10e810c3a0d5266049aa39f8a29d0021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b26aa43008d0b3fff48f3c8459c9866562639a280c31c3d8656cebe382cbf3e4 0.600000000000 1602017 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1120198, "vin": [ { "gen": { "height": 1120188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b26aa43008d0b3fff48f3c8459c9866562639a280c31c3d8656cebe382cbf3e4" } } ], "extra": [ 1, 68, 102, 172, 4, 74, 117, 95, 39, 182, 25, 102, 216, 190, 177, 176, 249, 74, 241, 14, 129, 12, 58, 13, 82, 102, 4, 154, 163, 159, 138, 41, 208, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8