Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fb27a0cca3cb503081b8024e8b3115d404aa301da674e1a76b33350e886e61e

Tx prefix hash: 42904347d5bb57e2a2df06f6dee6339356b1352ead854b82d0b3b81128971082
Tx public key: ea6590b68e55df2b1e4a77099533087a63cc6765c36c24b4e5eb892205e6e3f8
Timestamp: 1710770863 Timestamp [UCT]: 2024-03-18 14:07:43 Age [y:d:h:m:s]: 00:239:23:24:24
Block: 981066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171786 RingCT/type: yes/0
Extra: 01ea6590b68e55df2b1e4a77099533087a63cc6765c36c24b4e5eb892205e6e3f802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9855100d42ec96628ae7b32433b137241bf9baa62677ec9f665f18ac8d4a95d 0.600000000000 1441157 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": 981076, "vin": [ { "gen": { "height": 981066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9855100d42ec96628ae7b32433b137241bf9baa62677ec9f665f18ac8d4a95d" } } ], "extra": [ 1, 234, 101, 144, 182, 142, 85, 223, 43, 30, 74, 119, 9, 149, 51, 8, 122, 99, 204, 103, 101, 195, 108, 36, 180, 229, 235, 137, 34, 5, 230, 227, 248, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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