Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 451ec8feb9c77aa55c68878247ab9e918a0fe4d8d26fd04398c34ef97d769fc7

Tx prefix hash: 6e02c534136a9b5c7bc1406d3cd72c7be6fc8c5a56180d2ca5c7570c30a89f7e
Tx public key: 1d15601ff1a75dfb969c0116bb851725682bea05d1cfa018d0e6f707e60e95a1
Timestamp: 1702616110 Timestamp [UCT]: 2023-12-15 04:55:10 Age [y:d:h:m:s]: 01:126:03:17:35
Block: 913425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351305 RingCT/type: yes/0
Extra: 011d15601ff1a75dfb969c0116bb851725682bea05d1cfa018d0e6f707e60e95a1021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4c32b524b131ff053115a6ada4fd183a565541d79220556defc429361e90bcb 0.600000000000 1370693 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": 913435, "vin": [ { "gen": { "height": 913425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4c32b524b131ff053115a6ada4fd183a565541d79220556defc429361e90bcb" } } ], "extra": [ 1, 29, 21, 96, 31, 241, 167, 93, 251, 150, 156, 1, 22, 187, 133, 23, 37, 104, 43, 234, 5, 209, 207, 160, 24, 208, 230, 247, 7, 230, 14, 149, 161, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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