Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e347dd2451db706b0c8fb01de5cd859cc20e503e769a3d180d4863e85a90b8a

Tx prefix hash: fbf3b2e8107a6a7dbedb7aa7b6317c65e6e875909de5e05db57693f41422e186
Tx public key: 270a1f1419252dfd0eb16f8117f8eac52422bb2428c77e30caed483e7315f790
Timestamp: 1754399359 Timestamp [UCT]: 2025-08-05 13:09:19 Age [y:d:h:m:s]: 00:015:05:59:15
Block: 1340812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9961 RingCT/type: yes/0
Extra: 01270a1f1419252dfd0eb16f8117f8eac52422bb2428c77e30caed483e7315f79002110000000bb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38dea51e3e925fd78f628846d7e705785d4151d31fd8b584ae04f5d0117acb69 0.600000000000 1828633 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": 1340822, "vin": [ { "gen": { "height": 1340812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38dea51e3e925fd78f628846d7e705785d4151d31fd8b584ae04f5d0117acb69" } } ], "extra": [ 1, 39, 10, 31, 20, 25, 37, 45, 253, 14, 177, 111, 129, 23, 248, 234, 197, 36, 34, 187, 36, 40, 199, 126, 48, 202, 237, 72, 62, 115, 21, 247, 144, 2, 17, 0, 0, 0, 11, 178, 247, 132, 196, 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