Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f49619ab06930e652fce6931199217823d2d71a4c7db20f3de6b94b17d8f9fb

Tx prefix hash: 886d34a5bdd1a8a111f273b08e5b0f2a616cdafd9e3338ce9a97b56e37df7a2d
Tx public key: 2c1f7464673978714bf4a18591cf0d2d693a2e1a83dc89e50cb6768c096350c7
Timestamp: 1723882411 Timestamp [UCT]: 2024-08-17 08:13:31 Age [y:d:h:m:s]: 00:298:19:10:10
Block: 1089751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213429 RingCT/type: yes/0
Extra: 012c1f7464673978714bf4a18591cf0d2d693a2e1a83dc89e50cb6768c096350c7021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 440509fe867e9e94506f6a2d8a16c004235a2bd003e70f4deb965fdc9cb5921f 0.600000000000 1564374 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": 1089761, "vin": [ { "gen": { "height": 1089751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "440509fe867e9e94506f6a2d8a16c004235a2bd003e70f4deb965fdc9cb5921f" } } ], "extra": [ 1, 44, 31, 116, 100, 103, 57, 120, 113, 75, 244, 161, 133, 145, 207, 13, 45, 105, 58, 46, 26, 131, 220, 137, 229, 12, 182, 118, 140, 9, 99, 80, 199, 2, 17, 0, 0, 0, 6, 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