Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549091f40a1a8e41619ace4fee34b05e11d6961eaa418ec3bf8fef54bc09f11e

Tx prefix hash: 06da9417e131209132e713ed9904fcc9b003f641a9df1e993d289352b7918f96
Tx public key: eacd81a2a5ddf30a020d37e1f66e0af920f004140102cc12e0c778f39792c5ac
Timestamp: 1705067563 Timestamp [UCT]: 2024-01-12 13:52:43 Age [y:d:h:m:s]: 01:121:08:10:19
Block: 933749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347842 RingCT/type: yes/0
Extra: 01eacd81a2a5ddf30a020d37e1f66e0af920f004140102cc12e0c778f39792c5ac0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6751a2a95663bdaf5def93f19c8a17edd5cd72d3b6e4de1f7d8d51b70b3cfd25 0.600000000000 1391719 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": 933759, "vin": [ { "gen": { "height": 933749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6751a2a95663bdaf5def93f19c8a17edd5cd72d3b6e4de1f7d8d51b70b3cfd25" } } ], "extra": [ 1, 234, 205, 129, 162, 165, 221, 243, 10, 2, 13, 55, 225, 246, 110, 10, 249, 32, 240, 4, 20, 1, 2, 204, 18, 224, 199, 120, 243, 151, 146, 197, 172, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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