Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 909ffce07aa4b64d0d7fe877be3c8303378a4e1b9572019a4d874bfd254f9a5a

Tx prefix hash: a98c5833c20f282f3b0cd4080da9321ad1827f986b24af5f52b631e25b533999
Tx public key: bb576048e022d626e23feceec72a59fe04551e3af5a91f6e081f9e27871fe3e7
Timestamp: 1724992154 Timestamp [UCT]: 2024-08-30 04:29:14 Age [y:d:h:m:s]: 00:285:00:07:39
Block: 1098931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203591 RingCT/type: yes/0
Extra: 01bb576048e022d626e23feceec72a59fe04551e3af5a91f6e081f9e27871fe3e702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e7cc241e0c852abcedce61d370ded6287d34265416a02317a693960b6199259 0.600000000000 1574820 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": 1098941, "vin": [ { "gen": { "height": 1098931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e7cc241e0c852abcedce61d370ded6287d34265416a02317a693960b6199259" } } ], "extra": [ 1, 187, 87, 96, 72, 224, 34, 214, 38, 226, 63, 236, 238, 199, 42, 89, 254, 4, 85, 30, 58, 245, 169, 31, 110, 8, 31, 158, 39, 135, 31, 227, 231, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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