Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45b94fae9295d1876d82e4ba872338bf926d6e5b46690347c0ae2794dad60b52

Tx prefix hash: 842244b68aa38c72b58fc0c72ce4f17011c138cbcca8cc4852879d3f6f7a26ca
Tx public key: 97092470885ff62589880b0d08830ad40f8c9066bd2fc6e73c070a12cbd77d6b
Timestamp: 1710713376 Timestamp [UCT]: 2024-03-17 22:09:36 Age [y:d:h:m:s]: 00:303:04:47:54
Block: 980587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217015 RingCT/type: yes/0
Extra: 0197092470885ff62589880b0d08830ad40f8c9066bd2fc6e73c070a12cbd77d6b021100000001a5df9d86000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 8e6681e0cd21cd961f60659b19a5cb2a4eb4544df87dfb4a497b9f30e30bd16a 0.600010000000 1440662 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": 980597, "vin": [ { "gen": { "height": 980587 } } ], "vout": [ { "amount": 600010000, "target": { "key": "8e6681e0cd21cd961f60659b19a5cb2a4eb4544df87dfb4a497b9f30e30bd16a" } } ], "extra": [ 1, 151, 9, 36, 112, 136, 95, 246, 37, 137, 136, 11, 13, 8, 131, 10, 212, 15, 140, 144, 102, 189, 47, 198, 231, 60, 7, 10, 18, 203, 215, 125, 107, 2, 17, 0, 0, 0, 1, 165, 223, 157, 134, 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