Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95685550f2ca4e5fec5085e6440b15b6b1a6c9daa37f438906d63e6ebc27cb29

Tx prefix hash: c3522bfbfd7c59b3c2c0d8192e99faeb0d6a1022062ba7271371820a89fe748e
Tx public key: d0594be7c255aca3e1f14a7334caefb75d383fada67b89714dcfd3d7341a7672
Timestamp: 1580885923 Timestamp [UCT]: 2020-02-05 06:58:43 Age [y:d:h:m:s]: 05:247:12:53:48
Block: 58846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1326815 RingCT/type: yes/0
Extra: 01d0594be7c255aca3e1f14a7334caefb75d383fada67b89714dcfd3d7341a767202110000000217786bcf000000000000000000

1 output(s) for total of 391.759551563000 dcy

stealth address amount amount idx
00: e5f2d17e556250fa4ee4b25fb7cee3761ef0c2a150e880d176b0bd70034c08c1 391.759551563000 108768 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": 58856, "vin": [ { "gen": { "height": 58846 } } ], "vout": [ { "amount": 391759551563, "target": { "key": "e5f2d17e556250fa4ee4b25fb7cee3761ef0c2a150e880d176b0bd70034c08c1" } } ], "extra": [ 1, 208, 89, 75, 231, 194, 85, 172, 163, 225, 241, 74, 115, 52, 202, 239, 183, 93, 56, 63, 173, 166, 123, 137, 113, 77, 207, 211, 215, 52, 26, 118, 114, 2, 17, 0, 0, 0, 2, 23, 120, 107, 207, 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