Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d627805b672f1438255d885187822b2827f05710d459913bb270dfa3f4d1b27

Tx prefix hash: 14527d95f97dec951adc09d7b54555e3c5f4dcbf3b5b57343890b2dd89aac2f6
Tx public key: 0b8e7eb755e8fd2872a73955d4d4393fb62abbcfafd4436e2ce3888b40c0f6bf
Timestamp: 1730658802 Timestamp [UCT]: 2024-11-03 18:33:22 Age [y:d:h:m:s]: 00:021:00:54:37
Block: 1145842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15056 RingCT/type: yes/0
Extra: 010b8e7eb755e8fd2872a73955d4d4393fb62abbcfafd4436e2ce3888b40c0f6bf02110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a957c4f63174cb386cdb5e4df6f71161375d78ca90064fe65fddc257462e027b 0.600000000000 1630367 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": 1145852, "vin": [ { "gen": { "height": 1145842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a957c4f63174cb386cdb5e4df6f71161375d78ca90064fe65fddc257462e027b" } } ], "extra": [ 1, 11, 142, 126, 183, 85, 232, 253, 40, 114, 167, 57, 85, 212, 212, 57, 63, 182, 42, 187, 207, 175, 212, 67, 110, 44, 227, 136, 139, 64, 192, 246, 191, 2, 17, 0, 0, 0, 13, 31, 10, 83, 235, 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