Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d708e53a459e3de61eff5de3d54c83ec5ddafd2b9bd054eae2ddbfa5efb8026

Tx prefix hash: 348d0fe73d08ce1084149293029dfc30f102f282aa7d2663aa9e04c4eb70560e
Tx public key: d1f2770d1a8f5a03f1ce8db45741359f0cd2443a734e705c7bdb43d3ad344928
Timestamp: 1719243367 Timestamp [UCT]: 2024-06-24 15:36:07 Age [y:d:h:m:s]: 00:157:06:49:25
Block: 1051264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112574 RingCT/type: yes/0
Extra: 01d1f2770d1a8f5a03f1ce8db45741359f0cd2443a734e705c7bdb43d3ad344928021100000002a6fba9af000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1731bf1404c53193df12382956fb173804f5743f24e1ab29baca6796cd04e7eb 0.600000000000 1521573 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": 1051274, "vin": [ { "gen": { "height": 1051264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1731bf1404c53193df12382956fb173804f5743f24e1ab29baca6796cd04e7eb" } } ], "extra": [ 1, 209, 242, 119, 13, 26, 143, 90, 3, 241, 206, 141, 180, 87, 65, 53, 159, 12, 210, 68, 58, 115, 78, 112, 92, 123, 219, 67, 211, 173, 52, 73, 40, 2, 17, 0, 0, 0, 2, 166, 251, 169, 175, 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