Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cebc866b35d89e744f7d4cb738e6ae45fcee4cd70c112cbca1eaa9ccdad6589

Tx prefix hash: 19a201241e20faf4f759dcc210e1a91a8b1f394d5d7e30a636d8c80465d3ffae
Tx public key: 017c237a0450f2f3689ff8b8a1433aafe8b63e7f2d8a8582e49a197ba7af24a6
Timestamp: 1732867702 Timestamp [UCT]: 2024-11-29 08:08:22 Age [y:d:h:m:s]: 00:127:03:43:47
Block: 1164135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90693 RingCT/type: yes/0
Extra: 01017c237a0450f2f3689ff8b8a1433aafe8b63e7f2d8a8582e49a197ba7af24a6021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e482016368828d3649c94c9b93fc5574326f08d6355e73b8c518c1dee0101c0 0.600000000000 1649808 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": 1164145, "vin": [ { "gen": { "height": 1164135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e482016368828d3649c94c9b93fc5574326f08d6355e73b8c518c1dee0101c0" } } ], "extra": [ 1, 1, 124, 35, 122, 4, 80, 242, 243, 104, 159, 248, 184, 161, 67, 58, 175, 232, 182, 62, 127, 45, 138, 133, 130, 228, 154, 25, 123, 167, 175, 36, 166, 2, 17, 0, 0, 0, 2, 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