Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a59e4d0f24b3d7c9b522723b0e719f6de530e7bb723f899cdc59ba873ccee69

Tx prefix hash: ddfb6a8f6e40bafd89ad949830f1de9684be8b1e23e95383f5172f625de338bb
Tx public key: a0f979c1621b7db173afa563eef685f39858ceb1cc5ce1419f7d85936b5754ee
Timestamp: 1736136110 Timestamp [UCT]: 2025-01-06 04:01:50 Age [y:d:h:m:s]: 00:090:07:34:53
Block: 1191204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64323 RingCT/type: yes/0
Extra: 01a0f979c1621b7db173afa563eef685f39858ceb1cc5ce1419f7d85936b5754ee0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ca4e1245c1444e73f96ee54b1c7b9141d0f75a8e18c28ce4353ca79fd5b8687 0.600000000000 1677727 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": 1191214, "vin": [ { "gen": { "height": 1191204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ca4e1245c1444e73f96ee54b1c7b9141d0f75a8e18c28ce4353ca79fd5b8687" } } ], "extra": [ 1, 160, 249, 121, 193, 98, 27, 125, 177, 115, 175, 165, 99, 238, 246, 133, 243, 152, 88, 206, 177, 204, 92, 225, 65, 159, 125, 133, 147, 107, 87, 84, 238, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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