Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a61a0fa8456df15cbb9d29056d2843b2303450507cc3aa66f325f4f3ab1b1010

Tx prefix hash: 28e16bfd40678a45f1077ec591cf83fc57f50325cc8730bb8b2bba4b37fa9fa0
Tx public key: 8c41de4c415d08d7d44887ecdb4653e91887908d36ba2a2594595eec7cdd4e9a
Timestamp: 1709392178 Timestamp [UCT]: 2024-03-02 15:09:38 Age [y:d:h:m:s]: 01:069:16:28:55
Block: 969617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310827 RingCT/type: yes/0
Extra: 018c41de4c415d08d7d44887ecdb4653e91887908d36ba2a2594595eec7cdd4e9a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7de74eb4a6e1e2436b31c49ebd2431f4225639b2cc0b9132bab91d41598f7d9a 0.600000000000 1429454 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": 969627, "vin": [ { "gen": { "height": 969617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7de74eb4a6e1e2436b31c49ebd2431f4225639b2cc0b9132bab91d41598f7d9a" } } ], "extra": [ 1, 140, 65, 222, 76, 65, 93, 8, 215, 212, 72, 135, 236, 219, 70, 83, 233, 24, 135, 144, 141, 54, 186, 42, 37, 148, 89, 94, 236, 124, 221, 78, 154, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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