Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a95a832ee9e84e3edb919f6733cc9cc44c71bd46ce4433a115f01d9a330f75fb

Tx prefix hash: ccb90e1172016be159ad3b2ec8f5b19ce8774b547b823db1d12fd812d2f51441
Tx public key: 406f50d83f881b4f3a2273f83937c862494cd6edd330d128439849627c5555ba
Timestamp: 1700971027 Timestamp [UCT]: 2023-11-26 03:57:07 Age [y:d:h:m:s]: 01:340:15:01:41
Block: 899791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502329 RingCT/type: yes/0
Extra: 01406f50d83f881b4f3a2273f83937c862494cd6edd330d128439849627c5555ba02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.640647122000 dcy

stealth address amount amount idx
00: 47043d6df8a2bda780276a13c993ff93eba50512c5abd555d45523b5484e4b6e 0.640647122000 1356254 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": 899801, "vin": [ { "gen": { "height": 899791 } } ], "vout": [ { "amount": 640647122, "target": { "key": "47043d6df8a2bda780276a13c993ff93eba50512c5abd555d45523b5484e4b6e" } } ], "extra": [ 1, 64, 111, 80, 216, 63, 136, 27, 79, 58, 34, 115, 248, 57, 55, 200, 98, 73, 76, 214, 237, 211, 48, 209, 40, 67, 152, 73, 98, 124, 85, 85, 186, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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