Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffa42ae10bb29ecfb3bc1f070cd1502cafe8c42b0c41e35eaa369f47115cc519

Tx prefix hash: 9ba4ed2717ed838e441f4218f6960261b62c8bb30f98f07acf0e4e57fa4f45ca
Tx public key: b558138776a896620a3dba0f8e7a1c0d610d6b8fd8eb4b67aacdffb44e55effc
Timestamp: 1755251285 Timestamp [UCT]: 2025-08-15 09:48:05 Age [y:d:h:m:s]: 00:097:09:35:22
Block: 1347150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69291 RingCT/type: yes/0
Extra: 01b558138776a896620a3dba0f8e7a1c0d610d6b8fd8eb4b67aacdffb44e55effc02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7189d903c3f32cb8b780b975293a4d8755c0e3691827be54fe96565bda247a35 0.600000000000 1835065 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": 1347160, "vin": [ { "gen": { "height": 1347150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7189d903c3f32cb8b780b975293a4d8755c0e3691827be54fe96565bda247a35" } } ], "extra": [ 1, 181, 88, 19, 135, 118, 168, 150, 98, 10, 61, 186, 15, 142, 122, 28, 13, 97, 13, 107, 143, 216, 235, 75, 103, 170, 205, 255, 180, 78, 85, 239, 252, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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