Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb99732773f429f4d8ccecfb02768eee390359656e887f7574092c9365516e00

Tx prefix hash: b721c5af636f62935a354dd176512069c1c8dce43fa35b0f4c094c9fceb961a3
Tx public key: 9766d12740c5547ce0c8a2f50452db1a452087694cd2d9a3c65d447d90f8c36a
Timestamp: 1702288716 Timestamp [UCT]: 2023-12-11 09:58:36 Age [y:d:h:m:s]: 01:190:00:47:23
Block: 910722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396880 RingCT/type: yes/0
Extra: 019766d12740c5547ce0c8a2f50452db1a452087694cd2d9a3c65d447d90f8c36a021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01e53a578acd46f79331ccb88d89b60cda1199ca1b5fa1724391b9b1f83c4970 0.600000000000 1367889 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": 910732, "vin": [ { "gen": { "height": 910722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01e53a578acd46f79331ccb88d89b60cda1199ca1b5fa1724391b9b1f83c4970" } } ], "extra": [ 1, 151, 102, 209, 39, 64, 197, 84, 124, 224, 200, 162, 245, 4, 82, 219, 26, 69, 32, 135, 105, 76, 210, 217, 163, 198, 93, 68, 125, 144, 248, 195, 106, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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