Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b55f9f44f9ca99a09aea58ba13aad89261cab42c0796cdf0cf794d068645c862

Tx prefix hash: c30b0c0e33e240f4e1b152583f2bebeed20d9bf8e0dca88fbbd51da485b3dcb1
Tx public key: 59c35906ca19dd7ffd58a0ad7aa591edd7e3f52deb8e9920666ead895c549b9b
Timestamp: 1738163709 Timestamp [UCT]: 2025-01-29 15:15:09 Age [y:d:h:m:s]: 00:322:10:39:46
Block: 1207727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228246 RingCT/type: yes/0
Extra: 0159c35906ca19dd7ffd58a0ad7aa591edd7e3f52deb8e9920666ead895c549b9b0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c6899325dc4acfd4275a32c9ef655858e0e275528b30f4ed6f4f3e3ad3509f0 0.600000000000 1694452 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": 1207737, "vin": [ { "gen": { "height": 1207727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c6899325dc4acfd4275a32c9ef655858e0e275528b30f4ed6f4f3e3ad3509f0" } } ], "extra": [ 1, 89, 195, 89, 6, 202, 25, 221, 127, 253, 88, 160, 173, 122, 165, 145, 237, 215, 227, 245, 45, 235, 142, 153, 32, 102, 110, 173, 137, 92, 84, 155, 155, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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