Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53be2f5afffca390bcaabcf8c00189fea7403b9acf99852a0961e6c386a513a6

Tx prefix hash: 67f5422a1eb807f31d23b2d8b3fc10c04728f23c67d1d860e5caa72e10fc601c
Tx public key: 12b57bc74ad2dc8c18078685a53e84a0ec7c8e9078eb73c4d85be5a705c601d3
Timestamp: 1706448442 Timestamp [UCT]: 2024-01-28 13:27:22 Age [y:d:h:m:s]: 01:139:19:19:48
Block: 945179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360939 RingCT/type: yes/0
Extra: 0112b57bc74ad2dc8c18078685a53e84a0ec7c8e9078eb73c4d85be5a705c601d302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5c2c77d42a0e65ff6a153aa9f8ff33b50ad1bec0d469f9ff1618497e1e7049c 0.600000000000 1403489 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": 945189, "vin": [ { "gen": { "height": 945179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5c2c77d42a0e65ff6a153aa9f8ff33b50ad1bec0d469f9ff1618497e1e7049c" } } ], "extra": [ 1, 18, 181, 123, 199, 74, 210, 220, 140, 24, 7, 134, 133, 165, 62, 132, 160, 236, 124, 142, 144, 120, 235, 115, 196, 216, 91, 229, 167, 5, 198, 1, 211, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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