Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fd934c1c6ea4d7ccbdb3b2c302873102ca2a2c60095a75c755675ad8f0e6891

Tx prefix hash: 13970d5f56b74c8da88385945aef74857c440973980a4de8170b29e203468375
Tx public key: a471d2a8506d27a55e50abceabf289d76bf6afb175c9669f0fa2fae7006352d3
Timestamp: 1582984642 Timestamp [UCT]: 2020-02-29 13:57:22 Age [y:d:h:m:s]: 05:072:08:07:07
Block: 74143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1206010 RingCT/type: yes/0
Extra: 01a471d2a8506d27a55e50abceabf289d76bf6afb175c9669f0fa2fae7006352d302110000022b7adf42d3000000000000000000

1 output(s) for total of 348.605521311000 dcy

stealth address amount amount idx
00: 19cb162a41d41034cab15b656343fd42b6cbb55c8a6ce13a385deb27ed33b0f3 348.605521311000 137061 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": 74153, "vin": [ { "gen": { "height": 74143 } } ], "vout": [ { "amount": 348605521311, "target": { "key": "19cb162a41d41034cab15b656343fd42b6cbb55c8a6ce13a385deb27ed33b0f3" } } ], "extra": [ 1, 164, 113, 210, 168, 80, 109, 39, 165, 94, 80, 171, 206, 171, 242, 137, 215, 107, 246, 175, 177, 117, 201, 102, 159, 15, 162, 250, 231, 0, 99, 82, 211, 2, 17, 0, 0, 2, 43, 122, 223, 66, 211, 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