Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 556ddb32df0bc61e6a5a288e599a3b0fa9f680eee8f43c76b2da937c3effea84

Tx prefix hash: 755daa6019d68ac14ad1cae2e5292cc3998fcd8ed298c92bd0886126ed4d6c51
Tx public key: d2a2f48da1de6d1fb03da80757d241d429af1381b83efc404746c054b565ace7
Timestamp: 1759154853 Timestamp [UCT]: 2025-09-29 14:07:33 Age [y:d:h:m:s]: 00:119:14:18:32
Block: 1379046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85462 RingCT/type: yes/0
Extra: 01d2a2f48da1de6d1fb03da80757d241d429af1381b83efc404746c054b565ace702110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79a44f4b5f9d45c475e46d0627c501e7e31a5c81b9347a7878b35038885c15fc 0.600000000000 1867143 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": 1379056, "vin": [ { "gen": { "height": 1379046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79a44f4b5f9d45c475e46d0627c501e7e31a5c81b9347a7878b35038885c15fc" } } ], "extra": [ 1, 210, 162, 244, 141, 161, 222, 109, 31, 176, 61, 168, 7, 87, 210, 65, 212, 41, 175, 19, 129, 184, 62, 252, 64, 71, 70, 192, 84, 181, 101, 172, 231, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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