Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eff7a195aa9813f1c23c20baf482087cd524128bb32f92fe558481df3302edb7

Tx prefix hash: 481d0448b5daf6ad4ec32de4feb0e9051638aae46d2748a29d508e59fab9d6b0
Tx public key: 7277645e6cb64b9634dac8c75ede59f6fe69e2400056fe7c5bb0d856496f6ec2
Timestamp: 1699972558 Timestamp [UCT]: 2023-11-14 14:35:58 Age [y:d:h:m:s]: 01:123:21:34:19
Block: 891525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349739 RingCT/type: yes/0
Extra: 017277645e6cb64b9634dac8c75ede59f6fe69e2400056fe7c5bb0d856496f6ec202110000001333af99f4000000000000000000

1 output(s) for total of 0.682350605000 dcy

stealth address amount amount idx
00: 18cf5dab07b67de99d733804b03392eb245a3459c3dae3dee595bc1a86e0e8c4 0.682350605000 1347576 of 0

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": 891535, "vin": [ { "gen": { "height": 891525 } } ], "vout": [ { "amount": 682350605, "target": { "key": "18cf5dab07b67de99d733804b03392eb245a3459c3dae3dee595bc1a86e0e8c4" } } ], "extra": [ 1, 114, 119, 100, 94, 108, 182, 75, 150, 52, 218, 200, 199, 94, 222, 89, 246, 254, 105, 226, 64, 0, 86, 254, 124, 91, 176, 216, 86, 73, 111, 110, 194, 2, 17, 0, 0, 0, 19, 51, 175, 153, 244, 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