Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3ada45d9a82f0416f0ed29c640d076dbbb0ff0618fbf7c40aa328a4c678e65d

Tx prefix hash: e9856a75d3c1e1b560500811280097dabb8eb9b9e7a3cf059d09a3d7339a6b39
Tx public key: 6e74a00a8cde9a02e9eb18d35f3ff3375cbc98cbfd512be1bb18eb0370829008
Timestamp: 1733478152 Timestamp [UCT]: 2024-12-06 09:42:32 Age [y:d:h:m:s]: 00:114:21:27:43
Block: 1169197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81902 RingCT/type: yes/0
Extra: 016e74a00a8cde9a02e9eb18d35f3ff3375cbc98cbfd512be1bb18eb03708290080211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01fe0cc6cb4243c0c745dbbec48c141e113c18bcd5ae66bfd717098d2b0730d5 0.600000000000 1654912 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": 1169207, "vin": [ { "gen": { "height": 1169197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01fe0cc6cb4243c0c745dbbec48c141e113c18bcd5ae66bfd717098d2b0730d5" } } ], "extra": [ 1, 110, 116, 160, 10, 140, 222, 154, 2, 233, 235, 24, 211, 95, 63, 243, 55, 92, 188, 152, 203, 253, 81, 43, 225, 187, 24, 235, 3, 112, 130, 144, 8, 2, 17, 0, 0, 0, 2, 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