Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d3106d23ecbadb5e9d706914b24c528470f2bd02f79e1adead44237f936f9c2

Tx prefix hash: d1104a58b6ec893893fea98888aed1cdd3d20d252c533c53f10b27b00a9d75cd
Tx public key: cf6aaa3c129862ba0750f20f9d3852dd79b01364a083e883ac60a8cee2f40db6
Timestamp: 1724446373 Timestamp [UCT]: 2024-08-23 20:52:53 Age [y:d:h:m:s]: 00:060:10:32:52
Block: 1094440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43237 RingCT/type: yes/0
Extra: 01cf6aaa3c129862ba0750f20f9d3852dd79b01364a083e883ac60a8cee2f40db602110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3701f202507c8c15f9a22208f3cd45531eefb028deb4314303e3d93e384af0bd 0.600000000000 1569557 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": 1094450, "vin": [ { "gen": { "height": 1094440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3701f202507c8c15f9a22208f3cd45531eefb028deb4314303e3d93e384af0bd" } } ], "extra": [ 1, 207, 106, 170, 60, 18, 152, 98, 186, 7, 80, 242, 15, 157, 56, 82, 221, 121, 176, 19, 100, 160, 131, 232, 131, 172, 96, 168, 206, 226, 244, 13, 182, 2, 17, 0, 0, 0, 7, 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