Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e880a6edde1d976c0ec0222bfeb9a0422bed08cbd42499cac8c487c3c441ba2f

Tx prefix hash: 1b6a214c1ed59f4390deedfd2133a63176be42b13ab6d42579b1e70b0c826549
Tx public key: 9784f4625e0aa9e43024278120e96a87e98c21d5cdd643eeb0536860bda0324c
Timestamp: 1751166450 Timestamp [UCT]: 2025-06-29 03:07:30 Age [y:d:h:m:s]: 00:141:18:20:39
Block: 1314951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99408 RingCT/type: yes/0
Extra: 019784f4625e0aa9e43024278120e96a87e98c21d5cdd643eeb0536860bda0324c021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e3d404f092085396bc66e3ca67228ab6794f20c7a737807c694f0cf6afa6d4d 0.600000000000 1802604 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": 1314961, "vin": [ { "gen": { "height": 1314951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e3d404f092085396bc66e3ca67228ab6794f20c7a737807c694f0cf6afa6d4d" } } ], "extra": [ 1, 151, 132, 244, 98, 94, 10, 169, 228, 48, 36, 39, 129, 32, 233, 106, 135, 233, 140, 33, 213, 205, 214, 67, 238, 176, 83, 104, 96, 189, 160, 50, 76, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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