Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d545c08d68501c9a14a5f085b73c72fd6ee35736f8e11218cfc59d92a92187d

Tx prefix hash: 33c591bc9e0110e98e6724aaa2a02df372e23734cca14cf420d8e4a6033bcc6f
Tx public key: 79cf4af99939a5645dfc966a98a6571b1f23b7a68051fbece6f90d54e8039dfa
Timestamp: 1639323447 Timestamp [UCT]: 2021-12-12 15:37:27 Age [y:d:h:m:s]: 03:324:08:10:20
Block: 393997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1008267 RingCT/type: yes/0
Extra: 0179cf4af99939a5645dfc966a98a6571b1f23b7a68051fbece6f90d54e8039dfa021100000038de12510f000000000000000000

1 output(s) for total of 30.375591474000 dcy

stealth address amount amount idx
00: e1c6d84c7791c99df4a8a706b81b3704ef2b3134ef0788987897d65081fa6f7c 30.375591474000 791426 of 0

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": 394007, "vin": [ { "gen": { "height": 393997 } } ], "vout": [ { "amount": 30375591474, "target": { "key": "e1c6d84c7791c99df4a8a706b81b3704ef2b3134ef0788987897d65081fa6f7c" } } ], "extra": [ 1, 121, 207, 74, 249, 153, 57, 165, 100, 93, 252, 150, 106, 152, 166, 87, 27, 31, 35, 183, 166, 128, 81, 251, 236, 230, 249, 13, 84, 232, 3, 157, 250, 2, 17, 0, 0, 0, 56, 222, 18, 81, 15, 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