Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a2b109a49ceee8d773b444ec3ea5e1a53b84e39bb4162c1fd671e9a6d4305aa

Tx prefix hash: 490beec1ed6d8d7765feaf91e62455809940ede503f88c2530267b2d3c88aa04
Tx public key: abca70d9d6f40b5725f97c9e15ff3eb0ca6d376d6a2a40c91015a5d8a28beee2
Timestamp: 1714148612 Timestamp [UCT]: 2024-04-26 16:23:32 Age [y:d:h:m:s]: 01:194:01:41:39
Block: 1009043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397331 RingCT/type: yes/0
Extra: 01abca70d9d6f40b5725f97c9e15ff3eb0ca6d376d6a2a40c91015a5d8a28beee202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 393a4a7af48a926fa08458f16880e93d67d565d02683e3ea88162fe9a03ddc73 0.600000000000 1470597 of 15

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": 1009053, "vin": [ { "gen": { "height": 1009043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "393a4a7af48a926fa08458f16880e93d67d565d02683e3ea88162fe9a03ddc73" } } ], "extra": [ 1, 171, 202, 112, 217, 214, 244, 11, 87, 37, 249, 124, 158, 21, 255, 62, 176, 202, 109, 55, 109, 106, 42, 64, 201, 16, 21, 165, 216, 162, 139, 238, 226, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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