Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cca6e16d1de8bf271aa6da2cd51502842a7d72f04c3c34b9a7128d4fedb127fd

Tx prefix hash: 8f81ad3d05a0325bd1aa98783471968d4af3fae2fe471efc4ad31d56973db40a
Tx public key: 9fedee83ddba0db771dd0b3a8988236543a4db3b31244fea2de9ae653f448333
Timestamp: 1699859613 Timestamp [UCT]: 2023-11-13 07:13:33 Age [y:d:h:m:s]: 01:070:00:19:34
Block: 890577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311410 RingCT/type: yes/0
Extra: 019fedee83ddba0db771dd0b3a8988236543a4db3b31244fea2de9ae653f44833302110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.687303729000 dcy

stealth address amount amount idx
00: c92a0986ec6679ec098dd60eeea333029f5a7590810b1f5e3aef47255dd04c5e 0.687303729000 1346602 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": 890587, "vin": [ { "gen": { "height": 890577 } } ], "vout": [ { "amount": 687303729, "target": { "key": "c92a0986ec6679ec098dd60eeea333029f5a7590810b1f5e3aef47255dd04c5e" } } ], "extra": [ 1, 159, 237, 238, 131, 221, 186, 13, 183, 113, 221, 11, 58, 137, 136, 35, 101, 67, 164, 219, 59, 49, 36, 79, 234, 45, 233, 174, 101, 63, 68, 131, 51, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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