Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 529212166053a6fc976d76e2deb1181c18f01d8a3e42764dc0841b9d12d4dd93

Tx prefix hash: 492f7784d3cc01584b1d9aa68dfe3b08989348bf8a75e27893beb7df52cff292
Tx public key: 033bd384f390936932dd9e18abbe242421c4643bdff3629dc2b30c5790dc7173
Timestamp: 1707529795 Timestamp [UCT]: 2024-02-10 01:49:55 Age [y:d:h:m:s]: 01:123:01:43:46
Block: 954162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349019 RingCT/type: yes/0
Extra: 01033bd384f390936932dd9e18abbe242421c4643bdff3629dc2b30c5790dc71730211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7c8959d81c9fb0d9711d3b2422a8ed6d4f291d3919b036d1aa27b1dcba82024 0.600000000000 1413438 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": 954172, "vin": [ { "gen": { "height": 954162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7c8959d81c9fb0d9711d3b2422a8ed6d4f291d3919b036d1aa27b1dcba82024" } } ], "extra": [ 1, 3, 59, 211, 132, 243, 144, 147, 105, 50, 221, 158, 24, 171, 190, 36, 36, 33, 196, 100, 59, 223, 243, 98, 157, 194, 179, 12, 87, 144, 220, 113, 115, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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