Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99ec7679f33e5e0069f1bfedeb7b800b6f6c5144790084f66c523092b1381f5f

Tx prefix hash: 05e781054e6941eaa71bfbab9005de6e95bfbad053797698555b91b2d6aa95d6
Tx public key: d6bf05f5d5aab2685431f64e0ca1a70798e7b4c33262bb4177f2d9cfac2e2ee5
Timestamp: 1729993331 Timestamp [UCT]: 2024-10-27 01:42:11 Age [y:d:h:m:s]: 00:028:03:12:29
Block: 1140375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20082 RingCT/type: yes/0
Extra: 01d6bf05f5d5aab2685431f64e0ca1a70798e7b4c33262bb4177f2d9cfac2e2ee5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 739f0b29f617ae5dc35c8cab36877e1c5cd334428975425fc4c77e4f190f17a8 0.600000000000 1624170 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": 1140385, "vin": [ { "gen": { "height": 1140375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "739f0b29f617ae5dc35c8cab36877e1c5cd334428975425fc4c77e4f190f17a8" } } ], "extra": [ 1, 214, 191, 5, 245, 213, 170, 178, 104, 84, 49, 246, 78, 12, 161, 167, 7, 152, 231, 180, 195, 50, 98, 187, 65, 119, 242, 217, 207, 172, 46, 46, 229, 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