Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6d86c819e948aff48be57d1428d45df98fe05b4f1b1c2f7d43485e571c81299

Tx prefix hash: 72770e4d4ce5b44154f141b063dd8709a744b274f4140d9aacf6c078d4273b0d
Tx public key: d19735d0d5d6d4ffa70c1dd96538225c25ef7159be3800b2f0e95f3d9be51edf
Timestamp: 1707121484 Timestamp [UCT]: 2024-02-05 08:24:44 Age [y:d:h:m:s]: 01:013:14:42:41
Block: 950770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270740 RingCT/type: yes/0
Extra: 01d19735d0d5d6d4ffa70c1dd96538225c25ef7159be3800b2f0e95f3d9be51edf02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4613f996ccded04f0b707b60b198e79825e8cffce03ed42b54083798e0927ed1 0.600000000000 1409442 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": 950780, "vin": [ { "gen": { "height": 950770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4613f996ccded04f0b707b60b198e79825e8cffce03ed42b54083798e0927ed1" } } ], "extra": [ 1, 209, 151, 53, 208, 213, 214, 212, 255, 167, 12, 29, 217, 101, 56, 34, 92, 37, 239, 113, 89, 190, 56, 0, 178, 240, 233, 95, 61, 155, 229, 30, 223, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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