Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d610d769d8ddde7288887f5fcc14c97ca1f451fb816e06bd544e660d914ef08

Tx prefix hash: b3620cd345ce2f60c518804500a608dbea605806d0bc8682dfbb75005ae5615d
Tx public key: ace91a03a162e58b160666c2ea4e2f34e0f69c30728e2b6ee9dde88e1b3b89e2
Timestamp: 1736048290 Timestamp [UCT]: 2025-01-05 03:38:10 Age [y:d:h:m:s]: 00:092:15:24:18
Block: 1190475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65982 RingCT/type: yes/0
Extra: 01ace91a03a162e58b160666c2ea4e2f34e0f69c30728e2b6ee9dde88e1b3b89e2021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 079e5e9ffbca1955ea725c64c28dd44d157935cbd659f70664241db4ec12b256 0.600000000000 1676992 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": 1190485, "vin": [ { "gen": { "height": 1190475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "079e5e9ffbca1955ea725c64c28dd44d157935cbd659f70664241db4ec12b256" } } ], "extra": [ 1, 172, 233, 26, 3, 161, 98, 229, 139, 22, 6, 102, 194, 234, 78, 47, 52, 224, 246, 156, 48, 114, 142, 43, 110, 233, 221, 232, 142, 27, 59, 137, 226, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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