Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de45e4edc4bafb5299af5b6df819a385a8262b8257027c3290eb9f0cb479aa9f

Tx prefix hash: 1f1c605260a69730515ad89cda8058bf8294596d4e7959a0ee89850e6e6a8f8e
Tx public key: b399b85b67d18e75bb8a6a5758c3a93bf43f22c4f055935e75a7c4fbe2d12b9c
Timestamp: 1724679842 Timestamp [UCT]: 2024-08-26 13:44:02 Age [y:d:h:m:s]: 00:181:09:12:52
Block: 1096347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129467 RingCT/type: yes/0
Extra: 01b399b85b67d18e75bb8a6a5758c3a93bf43f22c4f055935e75a7c4fbe2d12b9c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 517901a413ca352e0f284dc289796a4d8961aa2745bdbe3c46c358a8c83d10e8 0.600000000000 1571536 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": 1096357, "vin": [ { "gen": { "height": 1096347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "517901a413ca352e0f284dc289796a4d8961aa2745bdbe3c46c358a8c83d10e8" } } ], "extra": [ 1, 179, 153, 184, 91, 103, 209, 142, 117, 187, 138, 106, 87, 88, 195, 169, 59, 244, 63, 34, 196, 240, 85, 147, 94, 117, 167, 196, 251, 226, 209, 43, 156, 2, 17, 0, 0, 0, 2, 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