Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4415c6c2458e2216a782db23b9c4f3871a62b3f09061f43e4aae944ad00b695

Tx prefix hash: b773ac10e5a4c682c79b683f45e0d4467d1c41c8275b2666de3828baa0e37669
Tx public key: c18a0a261050f96ab774f80e265e900b04af735e25cbc8ce6213eb53e87a8df4
Timestamp: 1579677874 Timestamp [UCT]: 2020-01-22 07:24:34 Age [y:d:h:m:s]: 04:345:19:30:57
Block: 50791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136791 RingCT/type: yes/0
Extra: 01c18a0a261050f96ab774f80e265e900b04af735e25cbc8ce6213eb53e87a8df4021100000059b221b3d1000000000000000000

1 output(s) for total of 416.606230528000 dcy

stealth address amount amount idx
00: b194fc558743046792820f9b7b698bcedd3e6234c1fde81cd59c8ab932005806 416.606230528000 94206 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": 50801, "vin": [ { "gen": { "height": 50791 } } ], "vout": [ { "amount": 416606230528, "target": { "key": "b194fc558743046792820f9b7b698bcedd3e6234c1fde81cd59c8ab932005806" } } ], "extra": [ 1, 193, 138, 10, 38, 16, 80, 249, 106, 183, 116, 248, 14, 38, 94, 144, 11, 4, 175, 115, 94, 37, 203, 200, 206, 98, 19, 235, 83, 232, 122, 141, 244, 2, 17, 0, 0, 0, 89, 178, 33, 179, 209, 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