Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58bb99f5e416c69d5eea278fd66b1f132d184e9d15a616d16e0735c533c8a4bd

Tx prefix hash: 610b4ea240a75c37bca23e437d264397ebbc5b8fab4135994a57e99a35474bf3
Tx public key: 83306e8560940975731cbf7ecda2f6c29ad0a65e1259d625bf8014a579f0144b
Timestamp: 1735964098 Timestamp [UCT]: 2025-01-04 04:14:58 Age [y:d:h:m:s]: 00:157:23:19:37
Block: 1189776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112724 RingCT/type: yes/0
Extra: 0183306e8560940975731cbf7ecda2f6c29ad0a65e1259d625bf8014a579f0144b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63eebcd1b7271840b38bb9c5c1f67d6d70414a245f685ee106eccd492b4b0a3e 0.600000000000 1676287 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": 1189786, "vin": [ { "gen": { "height": 1189776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63eebcd1b7271840b38bb9c5c1f67d6d70414a245f685ee106eccd492b4b0a3e" } } ], "extra": [ 1, 131, 48, 110, 133, 96, 148, 9, 117, 115, 28, 191, 126, 205, 162, 246, 194, 154, 208, 166, 94, 18, 89, 214, 37, 191, 128, 20, 165, 121, 240, 20, 75, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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