Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8349df02d433d522ffefc58f9cd2756bd1272b7370ff9868f529fe01de1ac7c

Tx prefix hash: 58d993aeab559ece3b8492733b3e60ee9d83906ca8f8f866444ecaa91db4656c
Tx public key: c919a2e110e9d482cc543ebd4526bf7a199e3f26934a8ee49f6ca9f4e14ece08
Timestamp: 1711770407 Timestamp [UCT]: 2024-03-30 03:46:47 Age [y:d:h:m:s]: 01:058:13:10:19
Block: 989347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302826 RingCT/type: yes/0
Extra: 01c919a2e110e9d482cc543ebd4526bf7a199e3f26934a8ee49f6ca9f4e14ece0802110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54a4e0d1046f2be9ae396b2cefee7572ef2aac3fdad2b18a9849d46b99a2479e 0.600000000000 1449644 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": 989357, "vin": [ { "gen": { "height": 989347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54a4e0d1046f2be9ae396b2cefee7572ef2aac3fdad2b18a9849d46b99a2479e" } } ], "extra": [ 1, 201, 25, 162, 225, 16, 233, 212, 130, 204, 84, 62, 189, 69, 38, 191, 122, 25, 158, 63, 38, 147, 74, 142, 228, 159, 108, 169, 244, 225, 78, 206, 8, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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