Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcbcb599a1b24164565ee8e30bdee2c2a6e8b81e6923fc77d9d6ab019d0bde0f

Tx prefix hash: 8755d3ce21bda78f1a1730e08a1c533f6f9ddf89b15ee19b3490f69353e2ea52
Tx public key: beff64d6a65f5ac5d3752f95fc8259534e092535f8c8b0502cef236ae0f3e20e
Timestamp: 1736777384 Timestamp [UCT]: 2025-01-13 14:09:44 Age [y:d:h:m:s]: 00:063:23:20:46
Block: 1196503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45512 RingCT/type: yes/0
Extra: 01beff64d6a65f5ac5d3752f95fc8259534e092535f8c8b0502cef236ae0f3e20e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03e26023699729e746ea6075367d99f1df0002eaf554d0ea2a466178e830b813 0.600000000000 1683102 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": 1196513, "vin": [ { "gen": { "height": 1196503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03e26023699729e746ea6075367d99f1df0002eaf554d0ea2a466178e830b813" } } ], "extra": [ 1, 190, 255, 100, 214, 166, 95, 90, 197, 211, 117, 47, 149, 252, 130, 89, 83, 78, 9, 37, 53, 248, 200, 176, 80, 44, 239, 35, 106, 224, 243, 226, 14, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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