Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01353a5c1ca37df8cd49cdcb4f0258e57b119366a5a08109284d4184071f07d8

Tx prefix hash: 7131e205f000e418a66ce55ec4f9a3d308686ef18e2764078240ea96e33dfcf2
Tx public key: d92cc2602563aa0437f8f5f16d782d60d8123fbee6f4a58355be100aaf307ebc
Timestamp: 1748741247 Timestamp [UCT]: 2025-06-01 01:27:27 Age [y:d:h:m:s]: 00:243:02:49:06
Block: 1295306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171343 RingCT/type: yes/0
Extra: 01d92cc2602563aa0437f8f5f16d782d60d8123fbee6f4a58355be100aaf307ebc021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fbafaeef88274bb20bd9ae75a0e716ca8822c7ecb159a5d8d7b4840cd1ddb56 0.600000000000 1782809 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": 1295316, "vin": [ { "gen": { "height": 1295306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fbafaeef88274bb20bd9ae75a0e716ca8822c7ecb159a5d8d7b4840cd1ddb56" } } ], "extra": [ 1, 217, 44, 194, 96, 37, 99, 170, 4, 55, 248, 245, 241, 109, 120, 45, 96, 216, 18, 63, 190, 230, 244, 165, 131, 85, 190, 16, 10, 175, 48, 126, 188, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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