Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e5bbf9159e54f41f291053c1773681db0d3ce2879b2a9ad477049be561e3caf

Tx prefix hash: 10d8a67c87f76f9732673d3e9c74023e640a9b829e149db09f7b1d25e66975d1
Tx public key: da4c7f92d1fbf0bbcfc94e7a61e01ee8b7896b78ad68d26da821d6ad76971b27
Timestamp: 1718890765 Timestamp [UCT]: 2024-06-20 13:39:25 Age [y:d:h:m:s]: 00:270:20:26:09
Block: 1048362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193546 RingCT/type: yes/0
Extra: 01da4c7f92d1fbf0bbcfc94e7a61e01ee8b7896b78ad68d26da821d6ad76971b270211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0c5425faada6193f17f368a9ebc37f3d570951b353de61a1c7537010f11f5ee 0.600000000000 1518431 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": 1048372, "vin": [ { "gen": { "height": 1048362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0c5425faada6193f17f368a9ebc37f3d570951b353de61a1c7537010f11f5ee" } } ], "extra": [ 1, 218, 76, 127, 146, 209, 251, 240, 187, 207, 201, 78, 122, 97, 224, 30, 232, 183, 137, 107, 120, 173, 104, 210, 109, 168, 33, 214, 173, 118, 151, 27, 39, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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