Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 482649d06e86e170b7445e7941e4feb42fb73e95b092ab44309dd0250f7e36d3

Tx prefix hash: 5745b120f3fb696b6d6fe183160d54faa62f440ebef6cf1c0ae5f32194afdc90
Tx public key: bc225381faa8eadf7dfa9e65f43220a3dc9ed54445171c2baa600233f673d2cb
Timestamp: 1648041842 Timestamp [UCT]: 2022-03-23 13:24:02 Age [y:d:h:m:s]: 03:223:11:07:52
Block: 464696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 937596 RingCT/type: yes/0
Extra: 01bc225381faa8eadf7dfa9e65f43220a3dc9ed54445171c2baa600233f673d2cb0211000000015eb576c5000000000000000000

1 output(s) for total of 17.712077538000 dcy

stealth address amount amount idx
00: 1451937be1b33aefe1cae1cfc7be5d3be90d5cf22cdeec2c6c8c8c66b29b6564 17.712077538000 882629 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": 464706, "vin": [ { "gen": { "height": 464696 } } ], "vout": [ { "amount": 17712077538, "target": { "key": "1451937be1b33aefe1cae1cfc7be5d3be90d5cf22cdeec2c6c8c8c66b29b6564" } } ], "extra": [ 1, 188, 34, 83, 129, 250, 168, 234, 223, 125, 250, 158, 101, 244, 50, 32, 163, 220, 158, 213, 68, 69, 23, 28, 43, 170, 96, 2, 51, 246, 115, 210, 203, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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