Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe85597eba9d4eb18b2c9538d3494a2659e9768a6ce3b5073f08457c3779c530

Tx prefix hash: 0e38547b95499c0c35cea536549d13b0821453a54fd55816c780b45cd3b146a7
Tx public key: 0a9817d2d88a84295f0f73a1cde7bccf7b9103659e81a53015c135733f804dfa
Timestamp: 1738687938 Timestamp [UCT]: 2025-02-04 16:52:18 Age [y:d:h:m:s]: 00:336:21:51:37
Block: 1212050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238628 RingCT/type: yes/0
Extra: 010a9817d2d88a84295f0f73a1cde7bccf7b9103659e81a53015c135733f804dfa02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3e2881f4506eb2e3caa4ce4e832a4440e1403e092aea14d63cbd61073ce6165 0.600000000000 1698817 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": 1212060, "vin": [ { "gen": { "height": 1212050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3e2881f4506eb2e3caa4ce4e832a4440e1403e092aea14d63cbd61073ce6165" } } ], "extra": [ 1, 10, 152, 23, 210, 216, 138, 132, 41, 95, 15, 115, 161, 205, 231, 188, 207, 123, 145, 3, 101, 158, 129, 165, 48, 21, 193, 53, 115, 63, 128, 77, 250, 2, 17, 0, 0, 0, 11, 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