Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 526a5a950a5e9c5a4748a4b0cec40d0e3140c94e1442419bbfc2228996f28957

Tx prefix hash: 3f26ecbb5f7d46c8c3965e62aef525adcf918b99d01bc8a5acc1f3a266adb4e2
Tx public key: b517e4c910d00d2de1a1bd214a3412cbe42ee4d83080b43dfb3b2746e3b5c101
Timestamp: 1702530400 Timestamp [UCT]: 2023-12-14 05:06:40 Age [y:d:h:m:s]: 01:037:06:22:36
Block: 912727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287952 RingCT/type: yes/0
Extra: 01b517e4c910d00d2de1a1bd214a3412cbe42ee4d83080b43dfb3b2746e3b5c10102110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfc65f60a1553a59e9e08d367871fcf9f37a1d9ba314780a528de52f1ca77697 0.600000000000 1369961 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": 912737, "vin": [ { "gen": { "height": 912727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfc65f60a1553a59e9e08d367871fcf9f37a1d9ba314780a528de52f1ca77697" } } ], "extra": [ 1, 181, 23, 228, 201, 16, 208, 13, 45, 225, 161, 189, 33, 74, 52, 18, 203, 228, 46, 228, 216, 48, 128, 180, 61, 251, 59, 39, 70, 227, 181, 193, 1, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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