Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8fd2d967eba9147c0935cc46fdfcc71f3a20650355a2d831a718dec5a1ed057

Tx prefix hash: c216ba41a1578edde91a46716088ea58bd53182cd58a02716089d15637e4f962
Tx public key: 5f64baa01c525b152a5f68a1a1a8668a56fd22be5549bc157bd3efb93fe9b27d
Timestamp: 1744568019 Timestamp [UCT]: 2025-04-13 18:13:39 Age [y:d:h:m:s]: 00:265:03:31:10
Block: 1260738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187293 RingCT/type: yes/0
Extra: 015f64baa01c525b152a5f68a1a1a8668a56fd22be5549bc157bd3efb93fe9b27d0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17aa10795cd4f1d426921683fa3bcf0d571b5cd905621d29a7e9c0892d9bc25f 0.600000000000 1747899 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": 1260748, "vin": [ { "gen": { "height": 1260738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17aa10795cd4f1d426921683fa3bcf0d571b5cd905621d29a7e9c0892d9bc25f" } } ], "extra": [ 1, 95, 100, 186, 160, 28, 82, 91, 21, 42, 95, 104, 161, 161, 168, 102, 138, 86, 253, 34, 190, 85, 73, 188, 21, 123, 211, 239, 185, 63, 233, 178, 125, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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