Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 266a156c1316d78ef9f985001c15d04d4cdf63adb50520be1b7d45656f08d70f

Tx prefix hash: 869ce9d89cfc90e5d602bc6cbc5ee8e7cdfa2b0de81ed5388c378241b8437643
Tx public key: dca0a4fe61b8d2321818ce80e2918449d098bb4a6a41caae9ef229c4d34ef048
Timestamp: 1726486415 Timestamp [UCT]: 2024-09-16 11:33:35 Age [y:d:h:m:s]: 00:115:10:20:34
Block: 1111334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82545 RingCT/type: yes/0
Extra: 01dca0a4fe61b8d2321818ce80e2918449d098bb4a6a41caae9ef229c4d34ef04802110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f512d94cd6387312bcb05be2d46781eb15e5c3b3b3e042eb2eba1cfa9b1d892b 0.600000000000 1590253 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": 1111344, "vin": [ { "gen": { "height": 1111334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f512d94cd6387312bcb05be2d46781eb15e5c3b3b3e042eb2eba1cfa9b1d892b" } } ], "extra": [ 1, 220, 160, 164, 254, 97, 184, 210, 50, 24, 24, 206, 128, 226, 145, 132, 73, 208, 152, 187, 74, 106, 65, 202, 174, 158, 242, 41, 196, 211, 78, 240, 72, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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