Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90f777b33b5f9374f1bcb4cb40d4e368d0e58a5deb3cd03029d1497ac4b16879

Tx prefix hash: f06c8d1c4268a2abac53f5310a07b5232080e3ad7b50e835f64663c073a26a02
Tx public key: 6ff61bd09913b7b8693debb7b2493348bbce1b7d0b5687b9deefe78acd50e3d4
Timestamp: 1681667635 Timestamp [UCT]: 2023-04-16 17:53:55 Age [y:d:h:m:s]: 01:349:13:33:17
Block: 739998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511111 RingCT/type: yes/0
Extra: 016ff61bd09913b7b8693debb7b2493348bbce1b7d0b5687b9deefe78acd50e3d40211000000025029cbac000000000000000000

1 output(s) for total of 2.168101730000 dcy

stealth address amount amount idx
00: 50883e99b34a9ed42efae322462308cfc5842436227c741c4751e6914601c4a7 2.168101730000 1186877 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": 740008, "vin": [ { "gen": { "height": 739998 } } ], "vout": [ { "amount": 2168101730, "target": { "key": "50883e99b34a9ed42efae322462308cfc5842436227c741c4751e6914601c4a7" } } ], "extra": [ 1, 111, 246, 27, 208, 153, 19, 183, 184, 105, 61, 235, 183, 178, 73, 51, 72, 187, 206, 27, 125, 11, 86, 135, 185, 222, 239, 231, 138, 205, 80, 227, 212, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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