Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f37341c38391c75c0193940206b212815182589d4ae9973774a726c79aef5f48

Tx prefix hash: e5ae164458be809d35f6e1fb4ccdbc5771a8ff1f57eb03db06d3c5297b4101e3
Tx public key: a655b048cf8df02d58ce4af8b165c114d8b129bf578b8d9e93514c34aaf9e312
Timestamp: 1720706288 Timestamp [UCT]: 2024-07-11 13:58:08 Age [y:d:h:m:s]: 00:254:16:04:53
Block: 1063420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181937 RingCT/type: yes/0
Extra: 01a655b048cf8df02d58ce4af8b165c114d8b129bf578b8d9e93514c34aaf9e31202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08d11be99fb36b4e88a2125ca4f0d802ebc58b74dff93bdc9578a3b469ad190a 0.600000000000 1533935 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": 1063430, "vin": [ { "gen": { "height": 1063420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08d11be99fb36b4e88a2125ca4f0d802ebc58b74dff93bdc9578a3b469ad190a" } } ], "extra": [ 1, 166, 85, 176, 72, 207, 141, 240, 45, 88, 206, 74, 248, 177, 101, 193, 20, 216, 177, 41, 191, 87, 139, 141, 158, 147, 81, 76, 52, 170, 249, 227, 18, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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