Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7435eb2dd854e3562f870ecce439b249737addf6c7a38a4d5a60e030e840b92

Tx prefix hash: c95359f2035c7da4782b5b11ef31da84956c4cadad8b35ed52db33dcb2407ca2
Tx public key: 3d05399b7762272de62cbce7ae4ae8b0946b09b8e644a07fb8d1a7099b791bef
Timestamp: 1706286457 Timestamp [UCT]: 2024-01-26 16:27:37 Age [y:d:h:m:s]: 01:071:22:44:03
Block: 943838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312512 RingCT/type: yes/0
Extra: 013d05399b7762272de62cbce7ae4ae8b0946b09b8e644a07fb8d1a7099b791bef0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9155185452f5fa5ad94c6ed7d2e50fa02355a46c1e63673805b7ff8d5f9697f4 0.600000000000 1402064 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": 943848, "vin": [ { "gen": { "height": 943838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9155185452f5fa5ad94c6ed7d2e50fa02355a46c1e63673805b7ff8d5f9697f4" } } ], "extra": [ 1, 61, 5, 57, 155, 119, 98, 39, 45, 230, 44, 188, 231, 174, 74, 232, 176, 148, 107, 9, 184, 230, 68, 160, 127, 184, 209, 167, 9, 155, 121, 27, 239, 2, 17, 0, 0, 0, 9, 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