Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2638b5bccd934386b8d15ab784be9a0ae8cd978006c52a0a92e566c437abf36

Tx prefix hash: 25a52738081e0e65da8d1397197587ce02837f8d1552ded725b618726e74cd6b
Tx public key: df89ac52e8a7b6bff091c675abe2871396d468e7a620fd5e22f83893e5a35699
Timestamp: 1765196667 Timestamp [UCT]: 2025-12-08 12:24:27 Age [y:d:h:m:s]: 00:028:12:03:33
Block: 1429122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20431 RingCT/type: yes/0
Extra: 01df89ac52e8a7b6bff091c675abe2871396d468e7a620fd5e22f83893e5a35699021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c6c64fbf4f10561e5a4a6f786f7774ffacaa3c07da464273d59fd8a11b36b41 0.600000000000 1917845 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": 1429132, "vin": [ { "gen": { "height": 1429122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c6c64fbf4f10561e5a4a6f786f7774ffacaa3c07da464273d59fd8a11b36b41" } } ], "extra": [ 1, 223, 137, 172, 82, 232, 167, 182, 191, 240, 145, 198, 117, 171, 226, 135, 19, 150, 212, 104, 231, 166, 32, 253, 94, 34, 248, 56, 147, 229, 163, 86, 153, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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