Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36edcd1f9940068b27dc7972f7c2f639a7e3c77e3c314bd4cdfc7ab908e529ee

Tx prefix hash: 9ada72d1dc56b89a05c8dab4a73e8b1269670446efb382b2294630eec0e8efea
Tx public key: 0aa3e6bc97f95d7bb4e4c5b6af34900a5c4eedd71a2ea15b1ea5039ca7b96f05
Timestamp: 1706288302 Timestamp [UCT]: 2024-01-26 16:58:22 Age [y:d:h:m:s]: 01:030:18:42:42
Block: 943850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283057 RingCT/type: yes/0
Extra: 010aa3e6bc97f95d7bb4e4c5b6af34900a5c4eedd71a2ea15b1ea5039ca7b96f050211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a20321de15ee07951133b9cc3d04bb19e06d006c72590de3ebd61c25ea1229ff 0.600000000000 1402076 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": 943860, "vin": [ { "gen": { "height": 943850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a20321de15ee07951133b9cc3d04bb19e06d006c72590de3ebd61c25ea1229ff" } } ], "extra": [ 1, 10, 163, 230, 188, 151, 249, 93, 123, 180, 228, 197, 182, 175, 52, 144, 10, 92, 78, 237, 215, 26, 46, 161, 91, 30, 165, 3, 156, 167, 185, 111, 5, 2, 17, 0, 0, 0, 7, 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