Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de693e46b46bdf8cb1bd74fe3df06a1363632d8c3e07696bc6fc90e1a5052c6f

Tx prefix hash: d03fc835af304849cde2f2e6a88f80738d5c45ff6a9a5e8651e27aa3e75eb168
Tx public key: 271c1777010314ae95f1e422275c24b4c9f7e4f44debd410306254a0bce15f3b
Timestamp: 1708671677 Timestamp [UCT]: 2024-02-23 07:01:17 Age [y:d:h:m:s]: 01:115:18:11:48
Block: 963641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343677 RingCT/type: yes/0
Extra: 01271c1777010314ae95f1e422275c24b4c9f7e4f44debd410306254a0bce15f3b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d160cefb3bc95042035484267587620cfc79f3323e3ad86f8ac7fa01f6419c8 0.600000000000 1423358 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": 963651, "vin": [ { "gen": { "height": 963641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d160cefb3bc95042035484267587620cfc79f3323e3ad86f8ac7fa01f6419c8" } } ], "extra": [ 1, 39, 28, 23, 119, 1, 3, 20, 174, 149, 241, 228, 34, 39, 92, 36, 180, 201, 247, 228, 244, 77, 235, 212, 16, 48, 98, 84, 160, 188, 225, 95, 59, 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