Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45b90df9dc9eea3c9731912fcc56d1bdd77a78b2873d8e022fe9508346a20fef

Tx prefix hash: 257345974037721d795f192b36c6042fb407c6deb9297210e59894a66bc98bb9
Tx public key: 918df74d8c1320f5e0522464a38228c10d59e947fd0e09df8d082996d7a06d2a
Timestamp: 1726464311 Timestamp [UCT]: 2024-09-16 05:25:11 Age [y:d:h:m:s]: 00:194:04:52:29
Block: 1111142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138623 RingCT/type: yes/0
Extra: 01918df74d8c1320f5e0522464a38228c10d59e947fd0e09df8d082996d7a06d2a021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45ff49651e2af90d2be2d8e80bc68170094bdd17254f92adef7f72abd8145e31 0.600000000000 1590001 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": 1111152, "vin": [ { "gen": { "height": 1111142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45ff49651e2af90d2be2d8e80bc68170094bdd17254f92adef7f72abd8145e31" } } ], "extra": [ 1, 145, 141, 247, 77, 140, 19, 32, 245, 224, 82, 36, 100, 163, 130, 40, 193, 13, 89, 233, 71, 253, 14, 9, 223, 141, 8, 41, 150, 215, 160, 109, 42, 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