Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 367b47f97939efba0b304e4f17a4f133d88d44efce924b37c9c2aaf37685bd99

Tx prefix hash: 6fd6394a782d8aadca404c9d1a945f376f474e6fc4772faa376367e4d0ac5db3
Tx public key: 974633ea8d366e60cc96b9b54734eefc6e9e7c314af9488a476d97a8233207b8
Timestamp: 1726216429 Timestamp [UCT]: 2024-09-13 08:33:49 Age [y:d:h:m:s]: 00:205:16:57:30
Block: 1109089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146841 RingCT/type: yes/0
Extra: 01974633ea8d366e60cc96b9b54734eefc6e9e7c314af9488a476d97a8233207b8021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2f0ab22dc3006017b72d99968135d2ab47838081b82997aca31103d2e7e6a99 0.600000000000 1587218 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": 1109099, "vin": [ { "gen": { "height": 1109089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2f0ab22dc3006017b72d99968135d2ab47838081b82997aca31103d2e7e6a99" } } ], "extra": [ 1, 151, 70, 51, 234, 141, 54, 110, 96, 204, 150, 185, 181, 71, 52, 238, 252, 110, 158, 124, 49, 74, 249, 72, 138, 71, 109, 151, 168, 35, 50, 7, 184, 2, 17, 0, 0, 0, 2, 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