Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e372922cc9a51bd5cd2dafaa412897c98ace87fbf73d6b1c5241109f2d435c8

Tx prefix hash: fa64c4d0907fd39f9c804e942760a67dca4de60386270793e000f846788b31d2
Tx public key: 1a4512d973a2d4f67c1a27d7c8b35df76cca712ecdc37473a04059a14fdd83d0
Timestamp: 1735123046 Timestamp [UCT]: 2024-12-25 10:37:26 Age [y:d:h:m:s]: 00:176:12:15:15
Block: 1182819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125838 RingCT/type: yes/0
Extra: 011a4512d973a2d4f67c1a27d7c8b35df76cca712ecdc37473a04059a14fdd83d00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfc2f55f0a87661f3e3e687abde53614c890cff8111515fd9682c14b7c30c105 0.600000000000 1669258 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": 1182829, "vin": [ { "gen": { "height": 1182819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfc2f55f0a87661f3e3e687abde53614c890cff8111515fd9682c14b7c30c105" } } ], "extra": [ 1, 26, 69, 18, 217, 115, 162, 212, 246, 124, 26, 39, 215, 200, 179, 93, 247, 108, 202, 113, 46, 205, 195, 116, 115, 160, 64, 89, 161, 79, 221, 131, 208, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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