Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9de39367df0b855069aa844b19c14ddd52f8b9d2b62e0f494488a689fbb10786

Tx prefix hash: 566f36a3722fbaf0b8bb2e2378a5a15cd3ce0a3950bb6c8609645e96e4f190ad
Tx public key: 6bc9aa01b81f1b29fffb072bcd2f17da49f55cdb9f582fd10f42ad75d233b5c5
Timestamp: 1696473126 Timestamp [UCT]: 2023-10-05 02:32:06 Age [y:d:h:m:s]: 01:178:20:57:38
Block: 862704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388886 RingCT/type: yes/0
Extra: 016bc9aa01b81f1b29fffb072bcd2f17da49f55cdb9f582fd10f42ad75d233b5c5021100000004faf35c9c000000000000000000

1 output(s) for total of 0.850165663000 dcy

stealth address amount amount idx
00: 8cb16a5f25e6aa59e983e104f4c61336fccd6e46b4bc2b991092bfa510aca1e5 0.850165663000 1317138 of 0

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": 862714, "vin": [ { "gen": { "height": 862704 } } ], "vout": [ { "amount": 850165663, "target": { "key": "8cb16a5f25e6aa59e983e104f4c61336fccd6e46b4bc2b991092bfa510aca1e5" } } ], "extra": [ 1, 107, 201, 170, 1, 184, 31, 27, 41, 255, 251, 7, 43, 205, 47, 23, 218, 73, 245, 92, 219, 159, 88, 47, 209, 15, 66, 173, 117, 210, 51, 181, 197, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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