Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e78cc4ac8e9f5f1a4425f48508235c142bbd229335ae5975e338e6691bf18969

Tx prefix hash: 3b994be009023140507a72a053d59835ebc11d2a557465467a15bfe3a1052e56
Tx public key: 08b20fefae8a99800bf2e95f65181e8d9108e16a8a09e101c6899244ea5e7b4b
Timestamp: 1702695768 Timestamp [UCT]: 2023-12-16 03:02:48 Age [y:d:h:m:s]: 01:102:11:57:57
Block: 914093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334376 RingCT/type: yes/0
Extra: 0108b20fefae8a99800bf2e95f65181e8d9108e16a8a09e101c6899244ea5e7b4b02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89b6a6e3509b58a75094dccc1b5a23942b776c9b8ba7e935aba84bac7ea60b5f 0.600000000000 1371377 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": 914103, "vin": [ { "gen": { "height": 914093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89b6a6e3509b58a75094dccc1b5a23942b776c9b8ba7e935aba84bac7ea60b5f" } } ], "extra": [ 1, 8, 178, 15, 239, 174, 138, 153, 128, 11, 242, 233, 95, 101, 24, 30, 141, 145, 8, 225, 106, 138, 9, 225, 1, 198, 137, 146, 68, 234, 94, 123, 75, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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