Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fee2c597fe938a0dbd60fec0d552f0a53ef2d6d3431135403b00a0c21f6ef5c3

Tx prefix hash: 54fe300d562dee58f8bf2e9b3aea27109cdd6bd2d16d2c7ea3df43eda2f585b0
Tx public key: dd4d4d7778dd7173bd399f4dd8c9e25a6f49cc557c9138bc8ac44572a25a6d71
Timestamp: 1681076633 Timestamp [UCT]: 2023-04-09 21:43:53 Age [y:d:h:m:s]: 02:070:03:03:05
Block: 735102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572200 RingCT/type: yes/0
Extra: 01dd4d4d7778dd7173bd399f4dd8c9e25a6f49cc557c9138bc8ac44572a25a6d7102110000000275e3f0e9000000000000000000

1 output(s) for total of 2.250699843000 dcy

stealth address amount amount idx
00: f764ca9cdab37f35b15fa6939525289b6e5da3e880e7b71af4c31bbdd13fb54e 2.250699843000 1181391 of 0

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": 735112, "vin": [ { "gen": { "height": 735102 } } ], "vout": [ { "amount": 2250699843, "target": { "key": "f764ca9cdab37f35b15fa6939525289b6e5da3e880e7b71af4c31bbdd13fb54e" } } ], "extra": [ 1, 221, 77, 77, 119, 120, 221, 113, 115, 189, 57, 159, 77, 216, 201, 226, 90, 111, 73, 204, 85, 124, 145, 56, 188, 138, 196, 69, 114, 162, 90, 109, 113, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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