Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b43d63318825471f72005a5d9aaf7ce4122a94d7323d211fb53986fee98e216e

Tx prefix hash: d2e9e9278dd14758ad564a92d2a94dab01f3dbc3a76ea51d3499badc2e1efc8c
Tx public key: 927eebb510e5629525799ffdf2bfd3ddb510e8a404ad869c32258eeb67f31131
Timestamp: 1720369467 Timestamp [UCT]: 2024-07-07 16:24:27 Age [y:d:h:m:s]: 00:345:06:25:41
Block: 1060613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246629 RingCT/type: yes/0
Extra: 01927eebb510e5629525799ffdf2bfd3ddb510e8a404ad869c32258eeb67f31131021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 293f9199af6bf67bf99ba32371ff0f11b5a98ca701c2a559688282ae3b0c2af5 0.600000000000 1531098 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": 1060623, "vin": [ { "gen": { "height": 1060613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "293f9199af6bf67bf99ba32371ff0f11b5a98ca701c2a559688282ae3b0c2af5" } } ], "extra": [ 1, 146, 126, 235, 181, 16, 229, 98, 149, 37, 121, 159, 253, 242, 191, 211, 221, 181, 16, 232, 164, 4, 173, 134, 156, 50, 37, 142, 235, 103, 243, 17, 49, 2, 17, 0, 0, 0, 1, 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