Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e445526af6b54c005a10c263fef370367cb9f3d3a10ec758194845832cef47c

Tx prefix hash: 6b48f831e5a644f623496cdd2afb15c1fe2d3ac3f0056c93e7bee0111da6d1d4
Tx public key: 20d69bfe3ef4c09424ada6ef59e6910ecceb02365438836d6ea149f84b427a36
Timestamp: 1734797918 Timestamp [UCT]: 2024-12-21 16:18:38 Age [y:d:h:m:s]: 00:093:02:37:02
Block: 1180151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66291 RingCT/type: yes/0
Extra: 0120d69bfe3ef4c09424ada6ef59e6910ecceb02365438836d6ea149f84b427a360211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e3c099b954b62adb912a2baf9ede1355526d3b0a12007dd4ae44d0f993b667d 0.600000000000 1666556 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": 1180161, "vin": [ { "gen": { "height": 1180151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e3c099b954b62adb912a2baf9ede1355526d3b0a12007dd4ae44d0f993b667d" } } ], "extra": [ 1, 32, 214, 155, 254, 62, 244, 192, 148, 36, 173, 166, 239, 89, 230, 145, 14, 204, 235, 2, 54, 84, 56, 131, 109, 110, 161, 73, 248, 75, 66, 122, 54, 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