Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45eba327f195ef451f596d7dd7dc4fa028f48dfed39e75b29d4fac066a76f3bb

Tx prefix hash: 12f302fe02779dd7f20d949f399322665c0a604ee653e12a4e59b25373089db3
Tx public key: a83def508f3670a5a1404784208a2b3c5b8914305432882df4fc910df1d7c95e
Timestamp: 1753255109 Timestamp [UCT]: 2025-07-23 07:18:29 Age [y:d:h:m:s]: 00:023:11:18:39
Block: 1331491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15888 RingCT/type: yes/0
Extra: 01a83def508f3670a5a1404784208a2b3c5b8914305432882df4fc910df1d7c95e02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8099ff804c36958b3f76bf2d4c3dae5fb7adb34f3af154a8480852e8f171fe7f 0.600000000000 1819286 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": 1331501, "vin": [ { "gen": { "height": 1331491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8099ff804c36958b3f76bf2d4c3dae5fb7adb34f3af154a8480852e8f171fe7f" } } ], "extra": [ 1, 168, 61, 239, 80, 143, 54, 112, 165, 161, 64, 71, 132, 32, 138, 43, 60, 91, 137, 20, 48, 84, 50, 136, 45, 244, 252, 145, 13, 241, 215, 201, 94, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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