Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e8bb06bf8a7c8f233e6b7b659915de21bb32100f705a0f85af811414a97bee8

Tx prefix hash: 0c89b65d89a82c53b553d08bc324b1a970e202d6a34b511ed21ac779ac861416
Tx public key: 650ae72a677756c012609db5fc06ae41cf5cb32feb8b95b5fd26907831a3cd9d
Timestamp: 1731112176 Timestamp [UCT]: 2024-11-09 00:29:36 Age [y:d:h:m:s]: 00:139:18:54:23
Block: 1149601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99723 RingCT/type: yes/0
Extra: 01650ae72a677756c012609db5fc06ae41cf5cb32feb8b95b5fd26907831a3cd9d0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6989f304e1d78fa42945fa5a1ea9643eece37ea9dadf12eb075d482a07d004e 0.600000000000 1634712 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": 1149611, "vin": [ { "gen": { "height": 1149601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6989f304e1d78fa42945fa5a1ea9643eece37ea9dadf12eb075d482a07d004e" } } ], "extra": [ 1, 101, 10, 231, 42, 103, 119, 86, 192, 18, 96, 157, 181, 252, 6, 174, 65, 207, 92, 179, 47, 235, 139, 149, 181, 253, 38, 144, 120, 49, 163, 205, 157, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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