Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f3ec732584a2a116647fed5665346cd9b4728c990e9159d5947b29b91142e6

Tx prefix hash: 5cbff2cd0026a9b9968fc777226e4db0cc30965f0663b6bbf791e013345d9d4a
Tx public key: 9172e84af5048cce5cff639c7c5f2a42e2112310731502ce98b6ae2ff205537d
Timestamp: 1669121863 Timestamp [UCT]: 2022-11-22 12:57:43 Age [y:d:h:m:s]: 03:011:17:59:27
Block: 636645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 788742 RingCT/type: yes/0
Extra: 019172e84af5048cce5cff639c7c5f2a42e2112310731502ce98b6ae2ff205537d021100000001e6d27f9c000000000000000000

1 output(s) for total of 4.770926834000 dcy

stealth address amount amount idx
00: 16673eadb3e8dac0c7bfa5e08da42ab6f241f29986d017b6c908d9f284fc60dc 4.770926834000 1076105 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": 636655, "vin": [ { "gen": { "height": 636645 } } ], "vout": [ { "amount": 4770926834, "target": { "key": "16673eadb3e8dac0c7bfa5e08da42ab6f241f29986d017b6c908d9f284fc60dc" } } ], "extra": [ 1, 145, 114, 232, 74, 245, 4, 140, 206, 92, 255, 99, 156, 124, 95, 42, 66, 226, 17, 35, 16, 115, 21, 2, 206, 152, 182, 174, 47, 242, 5, 83, 125, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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