Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e26c63d0ea7ff2e7946acb522d3fb13443a5dc1d30382cd3d2a73a8ca4962f5b

Tx prefix hash: a9ee8f571ae200d1cc86bfb2f4fb4db4e7b82bc99151c48f6a1947d568da7084
Tx public key: 7473b914ebf02bd51b54e5453c95396af9f1b621d19699d7fe5bf0772dbf3d1a
Timestamp: 1731871332 Timestamp [UCT]: 2024-11-17 19:22:12 Age [y:d:h:m:s]: 00:128:13:18:42
Block: 1155884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91676 RingCT/type: yes/0
Extra: 017473b914ebf02bd51b54e5453c95396af9f1b621d19699d7fe5bf0772dbf3d1a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cd8ae994c7a6e7d21af181c5dd79dcf901d06b9c0acb8a04965b41e6bfc195b 0.600000000000 1641503 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": 1155894, "vin": [ { "gen": { "height": 1155884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cd8ae994c7a6e7d21af181c5dd79dcf901d06b9c0acb8a04965b41e6bfc195b" } } ], "extra": [ 1, 116, 115, 185, 20, 235, 240, 43, 213, 27, 84, 229, 69, 60, 149, 57, 106, 249, 241, 182, 33, 209, 150, 153, 215, 254, 91, 240, 119, 45, 191, 61, 26, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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