Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80047415b3647c9e6ad5baab821e93debeee2bb1a1f77eaf525540e06d444f2a

Tx prefix hash: 0cc35a7c42bb41b9f7225d2033715a49a80c5816db8ea4679f6bb77b48910957
Tx public key: 5f88a00581b9a10b580e0597cadc1acbb714b59dd25a5dd4d4a880b422db1afc
Timestamp: 1719911055 Timestamp [UCT]: 2024-07-02 09:04:15 Age [y:d:h:m:s]: 01:127:09:39:33
Block: 1056817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349573 RingCT/type: yes/0
Extra: 015f88a00581b9a10b580e0597cadc1acbb714b59dd25a5dd4d4a880b422db1afc0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d35f324391050b6c6051f986c2498d8a88ec7c6d794c5677a61aef9a76d9e6e 0.600000000000 1527246 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": 1056827, "vin": [ { "gen": { "height": 1056817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d35f324391050b6c6051f986c2498d8a88ec7c6d794c5677a61aef9a76d9e6e" } } ], "extra": [ 1, 95, 136, 160, 5, 129, 185, 161, 11, 88, 14, 5, 151, 202, 220, 26, 203, 183, 20, 181, 157, 210, 90, 93, 212, 212, 168, 128, 180, 34, 219, 26, 252, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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