Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cf6f06cd963481b572f4ca30bdf4a01352257d746db5d9e3cbfc7fc44a10f14

Tx prefix hash: 66743d0554fb53d25e0f6aea397647265fd52a394c317ccfe16a6bd2a21ed403
Tx public key: 5fcf138abfb877a8f989b191dcecdb163b63e23bdec00ad02a419c5863d480ba
Timestamp: 1581699120 Timestamp [UCT]: 2020-02-14 16:52:00 Age [y:d:h:m:s]: 04:286:06:45:42
Block: 64930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1096803 RingCT/type: yes/0
Extra: 015fcf138abfb877a8f989b191dcecdb163b63e23bdec00ad02a419c5863d480ba021100000002026b59f3000000000000000000

1 output(s) for total of 373.990669531000 dcy

stealth address amount amount idx
00: 5fa08f2c575123a9fe7beb3bf8f4d533a7ebc3c773da48bed155ae75ff12407c 373.990669531000 119842 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": 64940, "vin": [ { "gen": { "height": 64930 } } ], "vout": [ { "amount": 373990669531, "target": { "key": "5fa08f2c575123a9fe7beb3bf8f4d533a7ebc3c773da48bed155ae75ff12407c" } } ], "extra": [ 1, 95, 207, 19, 138, 191, 184, 119, 168, 249, 137, 177, 145, 220, 236, 219, 22, 59, 99, 226, 59, 222, 192, 10, 208, 42, 65, 156, 88, 99, 212, 128, 186, 2, 17, 0, 0, 0, 2, 2, 107, 89, 243, 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