Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a241cc86ed9e7268e22ce7230ae64e4310a700589ae16efc4b44ca63d057e52

Tx prefix hash: ecf5d339fbefb4ddf080c98007ed4babbc970aa5230523c8f844ae40a4af02aa
Tx public key: de1bfdc1761abd06e0ddebd5895c7ad9d39f7c4242456bf8cb65f33bd0ab29fd
Timestamp: 1702307606 Timestamp [UCT]: 2023-12-11 15:13:26 Age [y:d:h:m:s]: 01:120:05:08:37
Block: 910879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347045 RingCT/type: yes/0
Extra: 01de1bfdc1761abd06e0ddebd5895c7ad9d39f7c4242456bf8cb65f33bd0ab29fd02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8473f0e94aa473a0c615eacc30cdda8758486cecbe77f01ac1506865abc5cce6 0.600000000000 1368054 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": 910889, "vin": [ { "gen": { "height": 910879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8473f0e94aa473a0c615eacc30cdda8758486cecbe77f01ac1506865abc5cce6" } } ], "extra": [ 1, 222, 27, 253, 193, 118, 26, 189, 6, 224, 221, 235, 213, 137, 92, 122, 217, 211, 159, 124, 66, 66, 69, 107, 248, 203, 101, 243, 59, 208, 171, 41, 253, 2, 17, 0, 0, 0, 2, 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