Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b53d8acdf50ce2bbf215b69c8751d67baf6f2d287921e1964b5c26abc829f17

Tx prefix hash: 8960760e642436b2a550ac6bdbb0377f9dcf28c660ae7dc9a0f667e53835fc30
Tx public key: fd4395b17c6ff4a5652e29c9687be1f7583d25a65735b6dc8eb516049efbcf4e
Timestamp: 1717477160 Timestamp [UCT]: 2024-06-04 04:59:20 Age [y:d:h:m:s]: 00:325:05:03:05
Block: 1036651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232428 RingCT/type: yes/0
Extra: 01fd4395b17c6ff4a5652e29c9687be1f7583d25a65735b6dc8eb516049efbcf4e0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a32f05954d22f29714b9d638542c595b05c6f48bc6019371529ad81b7a2f9ecd 0.600000000000 1505180 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": 1036661, "vin": [ { "gen": { "height": 1036651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a32f05954d22f29714b9d638542c595b05c6f48bc6019371529ad81b7a2f9ecd" } } ], "extra": [ 1, 253, 67, 149, 177, 124, 111, 244, 165, 101, 46, 41, 201, 104, 123, 225, 247, 88, 61, 37, 166, 87, 53, 182, 220, 142, 181, 22, 4, 158, 251, 207, 78, 2, 17, 0, 0, 0, 4, 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